Conversation
Member
|
I think we need to handle the https redirect for higher CefSharp versions. I tried to raise the version before but people got stuck with a white screen. I forgot how to reproduce it reliably. |
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Had to handle Cefsharp and Webview2 differently :
Cefsharp :
Cefsharp had support for extensions but was buggy. In newer version, they dropped extension support.
But you can manually add extension with Chrome's built-in extension manager.
So in extra browser, I added a button that opens chrome's extension page.
Webview2 :
Webview2 supports extensions programmatically, but the user can't manage his extensions.
I added a button that opens a simple view that behaves like chrome's extension page in extra browser.